This will allow the use of modern Go dependency management and project management capabilities.

On every push and pull request that affects relevant files, check the Go module for:

- Common detectable errors in the code.
- Use of outdated APIs
- Code style violations
- Code formatting inconsistency
- Misconfiguration

golint imposes the important requirement that all exported API components have a doc comment.

From a purely technical sense, there is no reason for the developer to have exported AppVersion, since it is not used in
other packages of the project and the project is exclusively a standalone application; not a reusable package.

However, there is maybe a little bit of semantic sense to exporting AppVersion. The deploy.sh script uses this line of
the code, so in a way it is "exported", even though it is used in an janky manner that does not care anything about Go's
export framework.

So the export may communicate that this line is an "API" of sorts and that modifying it must be done with care.

Since the developer did not bother to provide any documentation, it is not clear what purpose this thing was intended to
serve. What is clear is that it does not serve any purpose now, so it must be removed.

This project is intended only as a standalone application; not as a reusable packge. It only has a single package. For
this reason, there is no reason to export functions.